It looks like @koushiro hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement at the following URL: https://cla.parity.io

Once you've signed, please reply to this thread with [clabot:check] to prove it.

Many thanks,

Parity Technologies CLA Bot

[clabot:check]

It looks like @koushiro signed our Contributor License Agreement. 👍

Many thanks,

Parity Technologies CLA Bot

Very much in favour of this. Without this change, the storage_keys! macro breaks.

Glad that you pointed this out!
However, on the other side the fix for storage_keys seems to be simple.

The way I'm working around this right now looks as follows:

pub struct Key {
    pub key: [u8; 32]
}

impl Key {
    pub fn new(key: [u8; 32]) -> Key {
        Key { key: key }
    }

    pub fn h256(&self) -> H256 {
        H256::from(self.key)
    }
}

#[macro_export]
macro_rules! storage_keys {
	() => {};
	($($name:ident),*) => {
		storage_keys!(0u8, $($name),*);
	};
	($count:expr, $name:ident) => {
		static $name: Key = Key { key: [$count, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] };
	};
	($count:expr, $name:ident, $($tail:ident),*) => {
		static $name: Key = Key { key: [$count, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] };
		storage_keys!($count + 1u8, $($tail),*);
	};
}

Essentially, I'm building my own key type for storage.

I ll merge it as soon as CI is okay with it.
The current CI reports an issue with Windows but it doesn't look right so I just restarted it.

@Robbepop travis windows is always broken and after they kicked out all people, it will probably never work.